Print

Select the link below to download the Web.config file of the default Sitecore CMS 6.4.1 rev. 110928 installation:

• Download the Web.config file of Sitecore CMS 6.4.1 rev. 110928

Below is the list of changes made to the Web.config file of Sitecore CMS 6.4.1 rev. 110928 as compared to the Web.config file of Sitecore CMS 6.4.1 rev. 110720:

1. Add a hashAlgorithmType="SHA1" attribute to the <membership …> element in the <system.web> section. In a default Sitecore installation, the membership element should look like this:
   
   <membership defaultProvider="sitecore" hashAlgorithmType="SHA1">
2. Add the following node in the <system.webServer><modules> section, just before the Sitecore.Nexus.Web.HttpModule:
   
   <add type="Sitecore.Web.RewriteModule, Sitecore.Kernel" name="SitecoreRewriteModule"/>
3. In the <expandInitialFieldValue> pipeline, a new processor named CheckSharedField has been added after the SkipStandardValueItems processor, so that the entire pipeline now looks like this:
   
   <expandInitialFieldValue help="Processors should derive from Sitecore.Pipelines.ExpandInitialFieldValue.ExpandInitialFieldValueProcessor">
     <processor type="Sitecore.Pipelines.ExpandInitialFieldValue.SkipStandardValueItems, Sitecore.Kernel"/>
     <processor type="Sitecore.Pipelines.ExpandInitialFieldValue.CheckSharedField, Sitecore.Kernel"/>
     <processor type="Sitecore.Pipelines.ExpandInitialFieldValue.ReplaceVariables, Sitecore.Kernel"/>
   </expandInitialFieldValue>
4. The following setting is obsolete and should be deleted from section <settings> if it is present:
   
   <!--  AUTHENTICATION TICKET TIMEOUT
         Specifies the number of minutes before an authentication ticket
         becomes invalid. The default is 480 minutes (8 hours).
   -->
   <setting name="Authentication.TicketTimeout" value="480"/>
5. Add the following setting to the <settings> section:
   
   <!--  AUTHENTICATION CLIENT SESSION TIMEOUT
         Specifies the number of minutes before Sitecore considers user authentication session tickets as expired.
         This setting is only relevant for users logging in to Sitecore Client and when the Sitecore license has a limited number
         of concurrent editors.
         All expired sessions will automatically be removed when a new user tries to log in and the maximum
         number of concurrent editors has been reached.
         The default is 60 minutes (1 hour).
   -->
   <setting name="Authentication.ClientSessionTimeout" value="60" />
6. Add the following setting to the <settings> section:
   
   <!--  CACHING - DISABLE CACHE SIZE LIMITS
         If true, Sitecore does not limit cache size growth and ignores any maximum cache sizes
         specified in the web.config file.           
         Enabling this setting can improve the application's performance in 64-bit environments
         by allowing Sitecore to take full advantage of the available memory.
         After setting this value to true, monitor the system at regular intervals, as this
         configuration can cause Sitecore to consume too much memory and cause Out Of Memory errors.
         It is only recommended to set the setting to true in 64-bit environments.
         Default value: false
   -->
   <setting name="Caching.DisableCacheSizeLimits" value="false" />
7. Add the following setting to the <settings> section:
   
   <!--  ENABLE SITE.CONFIG FILES
         If true, the SiteResolver pipeline processor checks for the existence of a "site.config"
         file in the physical subdirectory corresponding to the requested URL. If a "site.config"
         file exists, Sitecore uses that file to determine the context site (Sitecore.Context.Site)
         for the current request.
         For example, when processing a request for the URL http://site.com/parent/child.html,
         Sitecore first checks for the existence of <webroot>/parent/site.config.
         Syntax: The site.config files should contain the following XML markup:
           <site reference="[name of the site definition from the web.config]" />
         Default value: false
   -->
   <setting name="EnableSiteConfigFiles" value="false" />
8. Add the following setting to the <settings> section:
   
   <!--  MEDIA - CACHE FILE MEDIA BY MODIFIED DATE
         If true, in addition to varying by the standard media request parameters such as height and width,
         Sitecore varies media cache entries for file-based media by both file path and the last modification
         date of the media file.
         If false, Sitecore varies file media cache entries only by file path and standard media request
         parameters and does not account for the last modification date of the file. A false value decreases
         the number of file system I/O operations performed for each media request, but could cause Sitecore
         to serve stale data for file media items if a process other than the Sitecore CMS user interfaces
         initiated that change.
         Default value: true
   -->
   <setting name="Media.CacheFileMediaByModifiedDate" value="true" />
9. Add the following two settings to the <settings> section:
   
   <!--  MEDIA - RESIZING MAX HEIGHT
         Maximum height for dynamically resized images.
         If the requested height exceeds this value, Sitecore resizes the image to this height.
         A value of 0 disables this height limit.
         Default value: 1024
   -->
   <setting name="Media.Resizing.MaxHeight" value="1024" />
   <!--  MEDIA - RESIZING MAX WIDTH
         Maximum width for dynamically resized images.
         If the requested width exceeds this value, Sitecore resizes the image to this width.
         A value of 0 disables this width limit.
         Default value: 1280
   -->
   <setting name="Media.Resizing.MaxWidth" value="1280" />
10. Add the following setting to the <settings> section:
    
    <!--  SERIALIZATION - INVALID FILE NAME CHARS
          When generating file names that correspond to item names, the serialization API encodes the "$" and "%" characters, as well
          as any characters that are invalid in path names as returned by the System.IO.Path.GetInvalidFileNameChars() method.
          You can use this setting to specify additional characters that must be encoded, such as to meet the requirements of a source
          control system that does not allow specific characters in file names.
          Default value: ""
    -->
    <setting name="Serialization.InvalidFileNameChars" value="" />